Skip to content

fix: remove special characters from powershell script#56

Merged
AkairoDev merged 1 commit intoMiniMax-AI:mainfrom
joshleblanc:patch-2
Feb 14, 2026
Merged

fix: remove special characters from powershell script#56
AkairoDev merged 1 commit intoMiniMax-AI:mainfrom
joshleblanc:patch-2

Conversation

@joshleblanc
Copy link
Contributor

When I was attempting to follow the quick start guide, powershell threw a syntax error. Syntactically, the script is fine, but something about the special characters in the script can cause failure.

PS C:\Users\jlebl> & "$env:TEMP\setup-config.ps1"
At C:\Users\jlebl\AppData\Local\Temp\setup-config.ps1:44 char:1
+ } else {
+ ~
Unexpected token '}' in expression or statement.
At C:\Users\jlebl\AppData\Local\Temp\setup-config.ps1:62 char:3
+ } catch {
+   ~~~~~
Unexpected token 'catch' in expression or statement.
    + CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : UnexpectedToken

Removing these characters solved the issue.

@joshleblanc
Copy link
Contributor Author

Possibly related, zed can't run the acp server either, seems to get hung up on a character

026-01-31T17:25:03-04:00 WARN  [agent_servers::acp] agent stderr: UnicodeEncodeError: 'charmap' codec can't encode character '\u2705' in position 5: character maps to <undefined>

Which I believe is just the green checkmark emoji

@AkairoDev AkairoDev merged commit 3ce94b0 into MiniMax-AI:main Feb 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants